Add new eventStream API for async generators #336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The eventStream response helpers is based a lot on how useEffect works, you pass a function and that function returns another one that's used to cleanup any side-effect.
This is great for event emitters like API where you have a function used to subscribe to events and another to unsubscribe, e.g.
Or another common API is for cases where you get the unsubscribe function, e.g.
Both are great, but if you want to iterate an AsyncIterator, you will need to create a function just to have the async code inside it.
This PR introduce an alternative API that will help with this my splitting the
handle
andcleanup
functions.A more real-world example usage for this is using the OpenAI SDK.